Questions
2 of 6
1How would you design a high-availability, horizontally scalable Go backend service?
2How do you build a basic HTTP server using only the standard library?
3How would you implement graceful shutdown for an HTTP server handling long-lived connections?
4How do you implement rate limiting in a Go API — per user, per IP, and globally?
5How would you implement middleware in Go using the standard library pattern vs a framework?
6What are the trade-offs between REST and gRPC for internal Go microservices?
golanggolang
Basics
Data Structures
Interfaces and Types
Concurrency
Memory Management
Error Handling
Packages and Modules
Web and API Development
Databases and Storage
Testing
DevOps and Deployment
Standard Library
02 / 06

How do you build a basic HTTP server using only the standard library?

The net/http package provides everything needed for a production-ready HTTP server. Use a custom http.ServeMux and configure server timeouts to prevent slow-client attacks.

Production HTTP server setup
Production considerations
  1. 1

    Always set ReadTimeout, WriteTimeout, IdleTimeout — defaults are zero (no timeout = DoS vulnerability)

  2. 2

    Go 1.22 adds method and path parameter support to ServeMux: GET /users/{id}

  3. 3

    Use http.NewServeMux() not the default mux to avoid global state in tests

  4. 4

    Wrap with middleware for logging, auth, and panic recovery before registering with the server

  5. 5

    For HTTP/2 and TLS: use srv.ListenAndServeTLS(certFile, keyFile)